Security in agile software development: A practitioner survey

Context: Software security engineering provides the means to define, implement and verify in software products. is performed by following a development life cycle model or capability maturity model. However, agile methods processes, dominant industry, are viewed be conflict with these practices requirements. Objective: Empirically use impact of activities context development, as practiced developer professionals. Method: A survey (N=61) was among practitioners Finland regarding their 40 common perceived impact, conjunction 16 items activities. Results: The had measurable effect on selection practices. Perceived lower than rate would imply: This taken indicate bias, caused e.g. developers’ awareness only certain practices, difficulties applying into an iterative workflow. Security deemed have most were proactive took place early phases development. Conclusion: Systematic conformed, observed take requirement implementation phases. In general, taking also considered impactful. discrepancy between level many observed. prompts research methodological for better integration methods, tools.